Update constant-keyword.asciidoc #129053
Merged
Update constant-keyword.asciidoc #129053
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Change the field name `date` to `@timestamp` so that users will be able to follow along with documentation. If not, then the date field is mapped as a keyword, which confuses users.
|
Documentation preview: |
|
@iamhowardtheduck please enable the option "Allow edits and access to secrets by maintainers" on your PR. For more information, see the documentation. |
elasticsearchmachine
added
needs:triage
leemthompo
added
>docs
|
Pinging @elastic/es-docs (Team:Docs) |
elasticsearchmachine
removed
the
needs:triage
💔 Backport failedYou can use sqren/backport to manually backport by running |
💔 Backport failedYou can use sqren/backport to manually backport by running |
This was referenced Jun 6, 2025
💚 All backports created successfully
Questions ?Please refer to the Backport tool documentation |
leemthompo
pushed a commit
to leemthompo/elasticsearch
that referenced
this pull request
Jun 6, 2025
Change the field name `date` to `@timestamp` so that users will be able to follow along with documentation. If not, then the date field is mapped as a keyword, which confuses users. (cherry picked from commit 73c56a5)
leemthompo
pushed a commit
to leemthompo/elasticsearch
that referenced
this pull request
Jun 6, 2025
Change the field name `date` to `@timestamp` so that users will be able to follow along with documentation. If not, then the date field is mapped as a keyword, which confuses users. (cherry picked from commit 73c56a5)
elasticsearchmachine
pushed a commit
that referenced
this pull request
Jun 6, 2025
Change the field name `date` to `@timestamp` so that users will be able to follow along with documentation. If not, then the date field is mapped as a keyword, which confuses users. (cherry picked from commit 73c56a5) Co-authored-by: Peter Titov <[email protected]>
elasticsearchmachine
pushed a commit
that referenced
this pull request
Jun 6, 2025
Change the field name `date` to `@timestamp` so that users will be able to follow along with documentation. If not, then the date field is mapped as a keyword, which confuses users. (cherry picked from commit 73c56a5) Co-authored-by: Peter Titov <[email protected]>
leemthompo
added a commit
to leemthompo/elasticsearch
that referenced
this pull request
Jun 16, 2025
9.x version of elastic#129053
elasticsearchmachine
pushed a commit
that referenced
this pull request
Jun 16, 2025
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Change the field name
dateto@timestampso that users will be able to follow along with documentation. If not, then the date field is mapped as a keyword, which confuses users.